- 1 minutes to read
Recovery Pending
If you are reading this, something really bad has happened to one or more databases, please contact our support for further technical assistance
Always make sure to have access to a SQL backup, and make sure you belong to the SQL sysadmin role before any attempts are made to execute any commands to resolve this matter. You may lose data if you are not careful
Troubleshooting
1. Stop all Nodinite related services
First, make sure to stop all Nodinite related services:
- Logging Service
- Monitoring Service
- App Pools (Name of environment depends on your installation), review the IIS Authentication settings user guide for additional information
2. Recover database
To recover the reported database, use the following SQL script, replace [NodiniteConfig_Test] with the actual database name:
ALTER DATABASE [NodiniteConfig_Test] SET EMERGENCY;
GO
ALTER DATABASE [NodiniteConfig_Test] set single_user
GO
DBCC CHECKDB ([NodiniteConfig_Test], REPAIR_ALLOW_DATA_LOSS) WITH ALL_ERRORMSGS;
GO
ALTER DATABASE [NodiniteConfig_Test] set multi_user
GO
3. Restart Nodinite Services
Re-start all Nodinite services in the following order:
- App Pools (Name of environment depends on your installation), review the IIS Authentication settings user guide for additional information
- Monitoring Service
- Logging Service